Systems, methods and devices for remote power management and discovery

ABSTRACT

A power monitoring device (PMD) can perform real-time remote managing, status reporting and analysis on the health/condition of equipment connected to the PMD. For example, a PMD provides data such as whether the equipment connected is idling, fully operating, malfunctioning, etc. The PMD can turn the power on/off, trigger system alert, and perform time-delayed or special profile programming to manage and monitor equipment usage. A power signature identification capability can identify what equipment such as monitor, laptop, lighting equipment, etc., are being connected. A configuration can be used by the power management device based at least in part on the waveform information (e.g., device model, activity status, etc.). Real-time diagnosis and collection of energy consumption and usage pattern can be aggregated for planning and management. Asset management can be enabled by discovering which models of devices are active and connected to a predetermined power management device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/655,699, filed Jul. 20, 2017, titled “SYSTEMS, METHODS AND DEVICESFOR REMOTE POWER MANAGEMENT AND DISCOVERY,” which is hereby incorporatedby reference herein in its entirety.

TECHNICAL FIELD

The present disclosure relates to power management and more specificallyto remote power management and discovery.

BACKGROUND

A modern office space typically has multiple general purpose poweroutlets (GPOs) available to supply mains power to all manner of officeequipment. Such office equipment may include, for example, computers,monitors, laptop docking stations, printers, scanners, modems, routers,charging stations, and the like. Each desk, office, cubicle, orworkstation in an office space is typically associated with a set of oneor more GPOs to power a set of devices associated with an individualworker.

A fairly recent trend is the concept of hot-desking, whereby workers arenot assigned individual desks or workstations on a permanent orsemi-permanent basis. Instead, desks or workstations are allocated on adaily basis, through first-come, first-served or through a bookingsystem.

Such hot-desking implementations can help a business to save on realestate costs and power costs, particularly for those businesses in whichit is common for some percentage of the staff to be out of the office ona regular basis. In such circumstances, the business does not need toprovide real estate and other facilities based on the maximum number ofstaff, but rather can provide real estate and other facilities based onthe maximum number of staff expected to attend a worksite on any givenday.

The amount of electronic office equipment has increased significantlyover the years, from a simple desktop computer with a single monitor toa desktop computer with multiple monitors, laptop computers, tabletcomputing devices, smartphones, and the like. Each of these electronicdevices typically requires access to mains power supply for some or allof the working day. As the number of electronic devices has increased,so too have the power costs for businesses. However, the power loads,and resultant costs, are typically not distributed evenly across allworkers and worksites.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram representation of a power managementdevice consistent with embodiments disclosed herein.

FIG. 2 is a schematic block diagram representation of a power managementdevice consistent with embodiments disclosed herein.

FIG. 3 is a schematic block diagram representation of a power managementdevice with a network controller consistent with embodiments disclosedherein.

FIG. 4 is a schematic block diagram representation of a power managementdevice adapted to be used with existing power outlets consistent withembodiments disclosed herein.

FIG. 5 is a schematic block diagram representation of a power managementdevice adapted to be used with existing power outlets consistent withembodiments disclosed herein.

FIG. 6 is a schematic block diagram representation of a network of powermanagement devices consistent with embodiments disclosed herein.

FIG. 7 is a schematic block diagram representation of a system formanagement of a set of power management devices consistent withembodiments disclosed herein.

FIG. 8 illustrates a user interface for monitoring and controlling thesystem of FIG. 7 consistent with embodiments disclosed herein.

FIG. 9 is a flow diagram illustrating a method for self-diagnostics andoperation of an end device embodying a power management deviceconsistent with embodiments disclosed herein.

FIG. 10 is a schematic block diagram representation of a powermanagement device embodied in a power board consistent with embodimentsdisclosed herein.

FIG. 11 is a schematic block diagram representation of a standalonepower management device adapted to be coupled to existing electronicdevices consistent with embodiments disclosed herein.

FIG. 12 is a schematic block diagram representation of a system thatincludes a general purpose computer on which one or more embodiments ofthe present disclosure may be practised consistent with embodimentsdisclosed herein.

FIG. 13 is a schematic block diagram representation of a system thatincludes a general smartphone on which one or more embodiments of thepresent disclosure may be practised consistent with embodimentsdisclosed herein.

FIG. 14 illustrates a floorplan for an office building, showing sensorlocations consistent with embodiments disclosed herein.

FIG. 15 illustrates the floorplan of FIG. 14, overlaid with a referencegrid consistent with embodiments disclosed herein.

FIG. 16 is a graph showing energy consumption of the sensor locations ofthe floorplan of FIG. 14 consistent with embodiments disclosed herein.

FIG. 17 is an alternative graph showing energy consumption of the sensorlocations of the floorplan of FIG. 14 consistent with embodimentsdisclosed herein.

FIG. 18 is a schematic block diagram representation of a powermanagement device embodied in a power board, with a separate power meterfor each power outlet consistent with embodiments disclosed herein.

FIG. 19 is a schematic diagram illustrating a power management systemwith a power management device with an identification service consistentwith embodiments disclosed herein.

FIG. 20 is a schematic diagram illustrating a power management systemwith a power management device with local identification consistent withembodiments disclosed herein.

FIG. 21 is a diagram illustrating status determination using powerthresholds consistent with embodiments disclosed herein.

FIG. 22 is a diagram illustrating successful power signatureidentification using a power profile consistent with embodimentsdisclosed herein.

FIG. 23 is a diagram illustrating unsuccessful power signatureidentification using power profiles consistent with embodimentsdisclosed herein.

FIG. 24 is a diagram illustrating a screenshot of a dashboard using tagaggregation of power management devices consistent with embodimentsdisclosed herein.

FIG. 25 is a diagram illustrating a screenshot of an enhanced assetmanagement system consistent with embodiments disclosed herein.

FIG. 26 is system diagram illustrating a system configured to provideservices for managing power management devices consistent withembodiments disclosed herein.

FIG. 27 is a flow chart illustrating a method for power managementconsistent with embodiments disclosed herein.

FIG. 28 is schematic diagram of a computing system consistent withembodiments disclosed herein.

DETAILED DESCRIPTION

A detailed description of systems and methods consistent withembodiments of the present disclosure is provided below. While severalembodiments are described, it should be understood that the disclosureis not limited to any one embodiment, but instead encompasses numerousalternatives, modifications, and equivalents. In addition, whilenumerous specific details are set forth in the following description inorder to provide a thorough understanding of the embodiments disclosedherein, some embodiments can be practiced without some or all of thesedetails. Moreover, for the purpose of clarity, certain technicalmaterial that is known in the related art has not been described indetail in order to avoid unnecessarily obscuring the disclosure.

Techniques, apparatus and methods are disclosed that enable real-timeremote managing, status reporting and analysis on the health/conditionof equipment connected to the power monitoring device (also known as apower management device/system or PMD). This system monitors, manages aswell as collects energy consumption data (including power relatedinformation, other electrical parameters, metadata for real time andfuture analysis though hardware devices). It can also perform real timeand predefined system control based on data collected. It can be in asingle location or multiple locations realized through a wired orwireless network. For example, a PMD provides data such as whether theequipment connected is idling, fully operating, malfunctioning etc. ThePMD can turn the power on/off, trigger system alert, and performtime-delayed or special profile programming to manage and monitorequipment usage.

Techniques, apparatus and methods are disclosed that enable energyconsumption signature identification capability which can identify whatequipment, such as monitor, laptop, lighting equipment, etc., are beingconnected. For example, the PMD can even identify OEM brands if given alarge enough database of energy consumption signatures. Using asignature mapping process, the PMD can also identifyunknown/non-workspace-intended equipment being connected, such as amicrowave, refrigerator, toaster, etc. In some embodiments, the powermanagement device samples a power draw and provides the waveform to acentral service for identification. The central service can provide aconfiguration and/or commands to the power management device based atleast in part on the waveform information (e.g., device model, activitystatus, etc.).

Techniques, apparatus and methods are disclosed that enable real-timediagnosis and collection of power consumption, other electrical data,metadata and usage pattern for power needs, equipment infrastructure,workspace planning, etc. For example, a large enough database can bevery helpful for the infrastructure planning of company or governmententities.

Techniques, apparatus and methods are disclosed that enable assetmanagement by discovering which models of devices are active andconnected to a predetermined power management device. If the detectedmodel matches an expected model, the asset tag can be confirmed. Byconfirming detected models, asset management can move from an inventoryprocess to a missing-item search or mismatched-item search.

Techniques, apparatus and methods are disclosed that enable temperaturesensing of a power management device and/or devices that are active. Forexample, temperature sensing can be embedded in the power strip/powermanagement device or general purpose power outlets (GPOs). Temperaturesensing can be accomplished through a thermal couple or athermistor/sensor which tracks the actual temperature of the powermanagement device in case of localize heating due to a malfunctioning orover loading of devices.

Metadata collected can include measured energy consumptioncharacteristics and energy consumption data. Measured energy consumptioncharacteristics can include instantaneous voltage, average voltage,instantaneous amperage, instantaneous wattage, average wattage, etc.Energy consumption data can include power profile, current profile,electronics signature, electronic waveform, device temperature, etc. Thesystem can remotely managing power usage, meta data collections, powerprofiles recognition as well as system protection due to over power,over current, over voltage, over temperature.

In some embodiments, a method and system for measuring energyconsumption relating to one or more general purpose power outlets (GPOs)can be used, based on readings derived from a power management device.The measured energy consumption may then be utilised to evaluateworkspace utilisation based on the location of one or more of the GPOs.The power management device receives a mains power supply, which iscoupled by the device to a set of one or more power outlets. The powermanagement device includes a power meter and a microcontroller forcontrolling at least one relay, wherein the relay is coupled to at leastone of the power outlets.

FIG. 3 is a schematic block diagram representation of a power managementdevice 300 with a network controller 316. The power management deviceincludes a housing 310 that includes the network controller 316, whichis adapted to be coupled to an external communications network. Thecommunications network may be implemented using one or more wired orwireless connections, including a Local Area Network (LAN), Wide AreaNetwork (WAN), a virtual private network (VPN), cellular telephonynetwork, the Internet, or any combination thereof

The network controller 316 is coupled to a microcontroller 314, whichreceives power and thermal information from a multi-purpose electricalmeter/sensors network 312. These data include instantaneous and averagevoltage, amperage, wattage as well as power profile, current profile,electronics signatures/waveforms, device temperature, other meta dataetc. The meter 312/sensors network is coupled to an input mains powersupply 305 and a relay switch 318. The relay switch 318 is operated bythe microcontroller 314, in response to commands received over thenetwork via the network controller 316. The relay switch 318 is coupledto an external power outlet 330, represented in the drawing asalternating current (AC) out.

FIG. 1 is a schematic block diagram representation of a power managementdevice 100 adapted to communicate wirelessly with a remote server (notshown). The power management device 100 includes a wireless transceiver110 (which can include a transmitter), which in this example isconfigured to operate using the ZigBee (IEEE 802.15.4) wirelesscommunications protocol. The wireless transceiver 110 is coupled to anantenna 105, which may be located internally or externally with respectto a housing of the device 100.

The wireless transceiver 110 is also coupled to a microcontroller 120,which is programmed to control operation of a general purposeinput/output (I/O) module 130. The microcontroller 120 may beimplemented, for example, using the Maxim Integrated MAX71020Single-Chip Electricity Meter AFE, Texas Instruments MSP430F6736, orAnalog Devices ADE7116 Single Phase Energy Measurement IC. It will beappreciated that other microcontrollers may equally be utilised tocontrol operation of the I/O module 130.

In the example of FIG. 1, the I/O module 130 controls a set of relayswitches 150, 160, 170, 180, each of which is coupled to a power outlet(not shown). The I/O module 130 is coupled to a multi-purpose meter 140that is adapted to monitor power consumed and other electrical data bythe power outlets coupled to the relay switches 150, 160, 170, 180.

In operation, the microcontroller 120 is able to be controlled viacontrol signals transmitted from the remote server to the device 100 viathe antenna 105 and wireless transceiver 110, so as to instruct themicrocontroller 120 to control the I/O module 130 to turn on or off oneor more of the relay switches 150, 160, 170, 180. Further, readings fromthe multi-purpose meter/sensors network 140 are transmitted to the I/Omodule 130, which in turn forwards the meter readings to themicrocontroller 120 for transmission via the wireless transceiver 110and the antenna 105 to the remote server.

In one arrangement, the microcontroller 120 and wireless transceiver 110are implemented as an integrated unit. For example, the microcontroller120 and wireless transceiver 110 may be implemented using a singlesystem on a chip (SoC) device, such as the ATMEL SAM21-Cortex-M0+ SOCwith Zigbee wireless transceiver or the Texas InstrumentsCC2538-Cortex-M3 SOC with Zigbee wireless transceiver.

In one scenario, the remote server receives power meter readings over aperiod of time. When the multi-purpose meter/sensors network readingsdrop below a predefined threshold, it may be assumed that no electricaldevices connected to the relay switches 150, 160, 170, 180 are in useand thus the remote server can instruct the microcontroller 120 to shutdown one or more of the power outlets connected to the relay switches150, 160, 170, 180 to reduce standby loads or “vampire” loads.

FIG. 2 is a schematic block diagram representation of a power managementdevice 200 adapted to communicate wirelessly with a remote server (notshown). The power management device 200 includes a wired transmitter210, which in this example is an Ethernet connection adapted to becoupled to a communications network.

The transmitter 210 is also coupled to a microcontroller 220, which isprogrammed to control operation of a general purpose I/O module 230. TheI/O module 230 controls a set of relay switches 250, 260, 270, 280, eachof which is coupled to a power outlet (not shown). The I/O module 230 iscoupled to a power meter 240 that is adapted to monitor power consumedand other electrical data by the power outlets coupled to each of therelay switches 250, 260, 270, 280.

In one arrangement, the microcontroller 220 and transmitter 210 areimplemented as an integrated unit. For example, the microcontroller 220and transmitter 210 may be implemented using a single system on a chip(SoC) device, such as the Texas Instruments Stellaris Cortex-M3 SOC with10/100 Ethernet MAC with PHY or the ATMEL SAM7X ARM7 SOC with 10/100Ethernet MAC with PHY.

In operation, the microcontroller 220 is able to be controlled viacontrol signals transmitted from the remote server to the device 200 viathe transmitter 210, so as to instruct the microcontroller 220 tocontrol the I/O module 230 to turn on or off one or more of the relayswitches 250, 260, 270, 280. Further, readings from the power meter 240are transmitted to the I/O module 230, which in turn forwards the meterreadings to the microcontroller 220 for transmission via the Ethernettransmitter 210 to the remote server.

In one scenario, the remote server receives data readings over a periodof time. When the power meter readings drop below a predefinedthreshold, it may be assumed that no electrical devices connected to therelay switches 250, 260, 270, 280 are in use and thus the remote servercan instruct the microcontroller 220 to shut down one or more of thepower outlets connected to the relay switches 250, 260, 270, 280 toreduce standby loads or “vampire” loads.

While a power strip form factor is often referred to in this disclosurefor the sake of clarity, it should be recognized that other form factorsare contemplated, including flexible cable networks, in-wall plugs,power cubes, extension cords, etc. The embodiments disclosed should notbe limited to the form factor recited, but should be read to includeother form factors unless specifically disclaimed.

FIG. 10 is a schematic block diagram representation of a powermanagement device embodied in a four outlet power board 1000. The powerboard 1000, also known as a power strip, receives an AC mains supply1005, which is fed to a multi-purpose meter/sensors network 1060. A toppower rail 1090 feeds each of a first power outlet 1010, a second poweroutlet 1020, a third power outlet 1030, and a fourth power outlet 1040,all of which are connected in parallel.

The output of the first power outlet 1010 is connected to a first relay1015, which is coupled to a bottom power rail 1095 that returns to thepower meter 1060 in order to complete the circuit. The output of thesecond power outlet 1020 is connected to a second relay 1025. The outputof the third power outlet 1030 is connected to a third relay 1035. Theoutput of the fourth power outlet 1040 is connected to a fourth relay1045. The outputs of the second, third, and fourth relays 1025, 1035,and 1045 are all coupled to the bottom power rail 1095.

The power board 1000 further includes a transmitter 1055, which isadapted to couple the power board 1000 to an external communicationsnetwork. The transmitter 1055 may be implemented using wired or wirelesstechnologies, including, but not limited to, Ethernet, Universal SerialBus (USB), Wi-Fi, Bluetooth, ZigBee, SigFox, LoRa, 6LoWPAN, and thelike.

The power board 1000 also includes a microcontroller 1050, which iscoupled to the transmitter 1055. Where the transmitter 1055 isimplemented as a transceiver, an external user can send control signalsvia the external communications network to the transmitter 1055 and thento the microcontroller 1050. The microcontroller 1050 is also coupled toeach of the relays 1015, 1025, 1035, and 1045, via respective controllines 1065, 1070, 1075, 1080 which enable the microcontroller 1050 tocontrol the application of power to each of the respective power outlets1010, 1020, 1030, 1040.

In an alternative embodiment (not shown), a single relay controls theapplication of power to each of the set of power outlets 1010, 1020,1030, 1040. In such an arrangement, all of the power outlets 1010, 1020,1030, 1040 are controlled together, such that the power outlets 1010,1020, 1030, 1040 are all turned on or all turned off. In the arrangementshown in FIG. 10, the microcontroller 1050 is able to control power tothe power outlets 1010, 1020, 1030, 1040 independently.

The multi-purpose meter/sensor network 1060 records the aggregate powerconsumption across all of the power outlets 1010, 1020, 1030, 1040 andtransmits recorded power information to the microcontroller 1050. Themicrocontroller 1050 sends some or all of the recorded power informationto the transmitter 1055 for transmission to a remote server.

FIG. 11 is a schematic block diagram representation of a standalonepower management device 1100 adapted to be coupled to existingelectronic devices. In the example of FIG. 11, the power managementdevice 1100 is coupled to a power board 1170. However, it will beappreciated that the standalone management device 1100 may be coupled toany electronic device, including, but not limited to, a computer,monitor, lamp, fan, and the like.

The power management device 1100 includes an input connector 1110 forcoupling to a mains power supply 1105. The input connector 1110 may beimplemented, for example, using a standard power plug adapted to pluginto a standard power outlet for the particular jurisdiction in whichthe device 1110 is to operate. The input connector 1110 may be connecteddirectly to a housing of the power management device 1100 or,alternatively, may include a section of power cable to facilitate easeof coupling of the device 1100 to a power outlet. The mains power ispassed through the connector 1110 to a power meter 1120 and then to anoutput connector 1160, via a relay 1130. A microcontroller 1150 isadapted to turn the relay 1130 on and off to control flow of electricityfrom the input connector 1110 to the output connector 1160. The outputconnector 1160 may be implemented, for example, as a general purposeoutlet adapted to receive a standard electrical plug rated for theparticular jurisdiction in which the device 1100 is to operate. In onearrangement, the output connector 1160 is implemented using anAS/NZ61535.1 compliant connector from CMS Electracom, as such connectorsare commonly used in office fitouts.

The power meter 1120 is connected to the microcontroller 1150 andprovides power information to the microcontroller 1150 over time. Themicrocontroller 1150 is also connected to the relay 1130, so as tocontrol coupling of the input mains power supply from the inputconnector 1110 to the external connector 1160. The microcontroller 1150is further connected to a transmitter 1155. As described above withreference to the transmitter 1055 of FIG. 10, the transmitter 1155 maybe a wired or wireless transmitter implemented, for example, usingEthernet, Universal Serial Bus (USB), Wi-Fi, Bluetooth, ZigBee, SigFox,LoRa, 6LoWPAN, or any other appropriate transmission protocol. Thetransmitter 1155 is adapted to transmit power information received bythe microcontroller 1150 from the power meter 1120 to a remote server(not shown).

In the example of FIG. 11, the power management device is coupled to apower board 1170, which includes a set of four power outlets 1172, 1174,1176, 1178. The power board 1170 is connected to the output connector1160 by a power cord 1165, wherein a first conductor in the power cord1165 is an active conductor connected to an upper power rail 1180 of thepower board 1170 and a second conductor in the power cord 1165 is aneutral conductor connected to a lower power rail 1185 in the powerboard 1170.

In operation, the standalone power management device 1110 may be pluggedinto an existing power outlet using the input connector 1110 and anelectronic device may be coupled to the output connector 1160. The powermeter 1120 is then able to monitor power consumption and otherelectrical data of the device connected to the output connector 1160,whereupon the microcontroller 1150 controls transmission of the powerinformation via the transmitter 1155 to a remote server. In the exampleof FIG. 11, the power meter 1120 monitors the aggregate powerconsumption of all devices connected to the power outlets 1172, 1174,1176, 1178. Further, when the transmitter 1155 is implemented as atransceiver, the remote server can send instructions to themicrocontroller 1150, via the transmitter 1155, to turn power on or offby operating the relay 1130.

The management device 1100 may be optionally equipped with a displaydevice, such as an LED panel, for displaying power data derived from themulti-purpose meter/network sensors 1120. Such power data may include,for example, instantaneous power readings, average power readings,maximum power readings, minimum power readings, instantaneous voltagereadings, average voltage readings, instantaneous current readings,average current readings, temperature over a predefined time period,maximum readings, minimum readings, and the like. In one arrangement,the display device is associated with a user interface that enables auser to scroll through one or more power readings. The user interfacemay be implemented, for example, using buttons, a touch screen, or thelike.

FIG. 4 is a schematic block diagram representation of a standalone powermanagement device 400 adapted to be used with existing power outlets andfeaturing a wireless transceiver 410 implemented using the ZigBeecommunications protocol. The wireless transceiver 410 is coupled to amicrocontroller 420, which controls operation of a master relay 440. Asdescribed above with reference to the embodiment of FIG. 11, the relay440 controls delivery of power from a mains power supply to which themanagement device is connected to a connected device. Themicrocontroller 420 is also coupled to a power meter 430, which monitorsthe power consumed by the connected device and feeds power informationback to the microcontroller 420 for storage and/or transmission by thetransceiver 410.

FIG. 5 is a schematic block diagram representation of a power managementdevice 500 adapted to be used with existing power outlets and featuringa wired transceiver 510 implemented using the ZigBee communicationsprotocol. The wireless transceiver 510 is coupled to a microcontroller520, which controls operation of a master relay 540. As described abovewith reference to the embodiment of FIG. 11, the relay 540 controlsdelivery of power from a mains power supply to which the managementdevice is connected to a connected device. The microcontroller 520 isalso coupled to a power meter 530, which monitors the power consumed andother electrical data by the connected device and feeds powerinformation back to the microcontroller 520 for storage and/ortransmission by the transceiver 510.

In one arrangement, a method and system utilise one or more of the abovementioned power management devices to collect energy consumptioninformation and power profile from power outlets installed on a set ofdesks in an activity based working environment. When active work takesplace, energy consumption also takes place, due to every device that isplugged into an electrical system exhibiting a certain energy signatureor power profile. This information is measured through time and relayedback to a central data server for storage.

The transmission of data from the power management devices may use anycommunications network, including one or more wired or wirelessconnections, including a Local Area Network (LAN), Wide Area Network(WAN), a virtual private network (VPN), cellular telephony network, theInternet, or any combination thereof. As described above with referenceto FIG. 1, the power management device 100 uses a low power wirelesstransceiver 110 employing the ZigBee protocol. In other embodiments, thetransceiver 110 may be implemented using any suitable wirelesstransmission protocol, including, but not limited to, 3G, 4G, Wi-Fi,Bluetooth, LTE, or Low-Power Wide-Area Network (LPWAN) technologies,such as LTE-MTC, LoRa, NarrowBand IoT, or Sigfox. Over time, the datacollected is used to establish a trend on workspace utilisation byoverlaying energy consumption on a floorplan of activity basedworkspace. This information indicates hotspots, such as whether areascould be well utilised, over utilised or under utilised. The activitybased working environment may then be modified for more efficient use ofthe workspace.

Methods and systems of the present disclosure may be used to perform,but are not limited to, the following functions: (1) Track workspaceutilisation through time; (2) Track and manage energy consumptionthrough time; (2a) This concept allows power to be turned off remotelyand automatically allowing the possibility to achieve a 0 W idle; (2b)Allow precise control of what devices to turn on or off; and (3) Trackoverall health and operation of a work desk remotely. (4) Track andidentify devices connected through power profile/electronics signaturerecognition. (5) Monitor safety status and security risk.

FIG. 6 is a schematic block diagram representation of a network 600 ofpower management devices. In the example of FIG. 6, the network 600 usespower management devices employing the ZigBee wireless technology,wherein the power management devices are configured in a cluster treeconfiguration. Each end device is configured in a reduced functionalitymode for reduced power consumption, operations simplicity, and costeffectiveness. The end devices may be implemented, for example, usingone or more of the power board 1000 of FIG. 10 and/or the powermanagement device 1100 of FIG. 11. The end devices communicate to aZigBee router. Every ZigBee router is in turn managed by a ZigBeecoordinator, which in turn is connected back to a central server. Thisconfiguration allows efficient deployment and expansion as more enddevices are required, without impacting data traffic and capacity.

In one arrangement, a single ZigBee router is dimensioned to control upto 100 power management devices implemented using ZigBee transceivers atany time and a single ZigBee coordinator is able to control up to 5ZigBee routers. Such an arrangement allows a capacity of 500 powermanagement devices (i.e., sensors) that can be installed on 500 desksper floor. In a multi floor configuration, the network may be expandedby adding a ZigBee coordinator at every floor and follow up router andthen end device, in a manner consistent with that illustrated in FIG. 6.

FIG. 7 is a schematic block diagram representation of a system 700 formonitoring a set of power management devices. The system 700 includes aset of end devices 710, 715, 720, wherein each end device includes apower management device, such as those described above with reference toFIGS. 10 and 11. Each end device 710, 715, 720 communicates with sensorinfrastructure 725, wherein the sensor infrastructure 725 represents thetopology of connections among Zigbee coordinators and Zigbee routers fora particular implementation.

The system 700 also includes a central data server 735, which is coupledto a central control unit 730. The central control unit 730 is coupledto the sensor infrastructure 725. The central data server 735 is theremote server referred to in relation to FIG. 10 and FIG. 11 and acts asa central repository for all the energy consumption information, otherelectrical data, and/or metadata that is transmitted back to base fromthe end devices 710, 715, 720. The information is stored in a databaseformat consisting of time, energy consumption, other electrical data,metadata location and end device health.

In one arrangement, the central data server 735 has multiple networkinterfaces by which to couple to a set of ZigBee coordinators. In oneparticular implementation, each floor of a multi-floor workspaceoccupies one interface.

The central control unit 730 acts as a controller interface. The centralcontrol unit 730 displays all power information in real time, such asdevice operation and health. Any actions to be performed, such asremotely operating a single end device, are initiated from the centralcontrol unit 730. The central control unit 730 is adapted to transmitcontrol commands via the sensor infrastructure 725 for execution by therespective microcontrollers in the end devices 710, 715, 720. Thecentral control unit 730 is able to communicate with the respectivemicrocontrollers to operate the relays and thus control delivery ofpower through the end devices 710, 715, 720. The central control unit730 is also able to communicate with the central data server 735 forpulling out data history and trends.

In one arrangement, the central control unit 730 has an associated userinterface by which one or more users are able to control aspects of thesystem 700. In one implementation, the user interface is adapted to bedisplayed as a dashboard on a display of a computing device.

FIG. 8 illustrates a user interface 800 having a dashboard formonitoring and controlling the system of FIG. 7. The dashboard 800aggregates and displays the power information and other electrical data,and/or metadata collected from the various sensors in the system 700.Depending on the size of the workspace in which the power managementdevices are deployed, the dashboard 800 optionally presents powerinformation by building, by floor, and by table. Each table or a sectionrepresents an end device deployed within the work site. The sectiondisplays health and/or energy consumption information as a quicksummary. Clicking on the section shows more detailed operationalinformation and a set of controls that are available for that sensor.The user interface also shows an energy consumption heat map overlaid ona floor plan to show which area is under-utilised or over-utilised.

In the example of FIG. 8, the dashboard 800 provides informationrelating to a particular work site. In this instance, a first region 810indicates a building name or reference, which in this example is“BUILDING 1”. The first region displays a set of sensor locations 830,which in this example are arranged by desk or room.

A secondary region 840 provides further information for a selectedsensor location. In the example of FIG. 8, Table 3 is the selectedsensor location, and the second region 840 provides a table listing aset of sensors associated with Table 3 and their respective powerconsumption readings.

A third region 850 provides one or more graphical displays relating topower consumption regions associated with a selected area. In theexample of FIG. 8, the third region 850 displays information pertainingto the selected sensor location, Table 3. A first graph 860 maps energyconsumption, other electrical data, and/or metadata over time for Table3. A second graph 870 provides a graphical representation of a floorplanto identify a position of Table 3 in its local environment, which inthis example is FLOOR 1 of BUILDING 1.

FIGS. 14 to 17 illustrate an example in which the central data server735 generates an energy consumption heat map for a floor of an officebuilding. FIG. 14 illustrates a simplified floorplan 1400 of an officefloor having a showroom, a boardroom, three meeting rooms, two otherrooms, and 38 desks arranged across two columns.

To assist in identifying the relative locations of the different desksand rooms, FIG. 15 illustrates a grid overlaid on the floorplan 1400. Inthis example, a first, horizontal axis is labelled in units A-H and asecond, vertical axis is labelled in units 1-25. Thus Table 25 shown inFIG. 14 may be referenced using the co-ordinates (D,16).

Table 1 below illustrates an example of power figures obtained from thevarious desks and rooms of the floorplan 1400, referenced in accordancewith the grid of FIG. 15. Thus, Table 25, referenced as (D,16) has apower consumption figure of 500. Depending on the implementation and theapplication, the power consumption figure may be an instantaneousreading, an average reading over a predefined period of time, acumulative reading over a period of time, or any combination thereof. Inthis example, the power consumption figure of 500 corresponds to 500 Whover a period of a day.

TABLE 1 A B C D E F G H 1 0 50 0 0 0 0 0 0 2 400 0 0 0 0 0 0 0 3 0 0 0 00 0 0 0 4 100 0 0 0 100 0 0 0 5 5 5 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 7 40080 0 80 150 0 0 0 8 600 600 0 200 300 0 0 0 9 0 0 0 0 0 0 0 0 10 400 5000 5 40 0 0 0 11 500 500 0 10 150 0 0 0 12 0 0 0 0 0 0 0 0 13 300 180 0 00 0 0 0 14 100 5 0 0 0 0 0 0 15 0 0 0 0 0 0 0 0 16 120 60 0 500 30 0 150100 17 150 150 0 500 500 0 150 200 18 0 0 0 0 0 0 0 0 19 50 150 0 250 100 0 0 20 30 0 0 250 10 0 0 0 21 0 0 0 50 0 0 0 0 22 100 50 0 0 0 0 23 00 0 0 0 0 0 0 24 10 0 0 0 0 0 0 0 25 10 0 0 0 0 0 0 0

The power consumption figures shown in Table 1 are also overlaid on thefloorplan 1400 in FIG. 15. It can be seen from FIGS. 14 and 15 that twopower outlets in Meeting Room 1 (A, 24-25) have relatively low powerusage of 10 Wh each, whereas Tables 7 and 8, of the OperationsDepartment, have relatively high power usage figures of 600 Wh each.Similarly, Table 1 shows no power consumption in Column C, as thatregion of the floorplan corresponds to a corridor or walkway. Otherelectrical data and/or metadata can also be used in place of the powerconsumption data.

FIG. 16 shows an energy consumption heat map 1600 illustratingdistribution of energy consumption across the floorplan 1400. From theheat map 1600, it is readily apparent that some locations of thefloorplan 1400 use large amounts of power and other locations use smallamounts of power. Such information can be used to plan installation ofnew power outlets, distribution of workspaces, reallocation ofworkspaces, and the like.

FIG. 17 shows an alternative energy consumption heat map 1700illustrating distribution of energy consumption across the floorplan1400 from a top plan view. This view makes it easier to identifywalkways and unused office space. Different colours or shadingintensities may be used to differentiate different energy consumptionlevels.

In one arrangement, each end device performs a mandatory self-diagnostictest upon startup. This provides general information about the overallhealth of the desk to which the device is attached. In oneimplementation, a microcontroller on each end device performs theself-diagnostic test. The overall health of the desk to which the deviceis attached may be assessed based one or more parameters, including, forexample, but not limited to, transmitter link status, network status,feedback response from relays within the device, response from powermeter, and the like. The microcontroller may perform such aself-diagnostic test by executing computer code instructions stored on,or accessible by, the microcontroller.

If the self-diagnostic test reveals a problem, only the affected featureis disabled, so that unaffected features can continue to be used withoutaffecting uptime. This is only temporary, because the status is reportedto the command centre console for further action. For example, using theexample of FIG. 10, if the microcontroller 1050 detects that relay 1015,fails due to lack of response or an incorrect response during theself-diagnostic test, the microcontroller 1050 is able to disable relay1015 via the control line 1065. The microcontroller 1050 is then able toreport the fault to a central server via the transmitter 1055. In theevent that a fault resides in the transmitter 1055, then themicrocontroller 1050 would be unable to download new settings orpolicies or report power usage data back to the central server. In onearrangement, the microcontroller 1050 is adapted to bypass a defectivecomponent in order to maintain substantially normal operation. In onearrangement, the central server listens for a periodic heartbeat signalfrom each end device and issues an alert if a heartbeat signal is notreceived within a predefined time period.

Each sensor end device is assigned a sensor identifier (ID). The sensorID corresponds to a physical location at which the end device isdeployed. The dashboard of the control user interface is adapted todisplay the various sensor IDs. FIG. 9 is a flow diagram of aself-diagnostic test method 900. The method 900 begins at a Start step905 and proceeds to step 910, which performs the self-diagnostic test.

Decision step 915 determines whether there are any issues. If the selfdiagnostic test reveals no issues, No, control passes to step 920, whichchecks a policy. The policy determines what configuration has beenchosen by an organisation (e.g., switch on relay 1, switch off relay 2,etc.). In step 925, the system downloads and applies the settings andthen proceeds with normal operations. Control passes to decision step930. Step 930 determines the outcome from downloading settings thathappened in Step 925. If the settings are OFF (e.g., night mode), thenstep 930 triggers an “Off” countdown loop. If the settings are ON (e.g.,day mode), then step 930 triggers the normal loop. So, if step 930identifies an “ON” outcome, control passes to step 935. At predefinedtime intervals, the end device measures and transmits energy consumptioninformation, as shown in step 935. During normal operations, additionalsub flows are inserted to allow for on-the-go changes, to forceoverwrite during off peak use (e.g., employees returning to work outsideof normal hours), etc.

Control passes to step 940 which performs a countdown timer and thenproceeds to decision step 945. Decision step 945 determines whether acertain interval (e.g., >a certain uptime) has passed. If the intervalhas passed, Yes, the end device returns to the top of the flow chart tostep 910 to perform the self-diagnostic test again. This informationprovides a real-time effect to the command centre console on the overallhealth of the entire building or floor.

However, if at step 945 the interval has not expired, No, control passesto step 960, which listens for instructions. For example, if thecountdown timer is set to a predefined first timer interval of 30minutes and the interval is set to 8 hours, then steps 940, 945, and 960in combination will listen for new instructions every 30 minutes for upto 8 hours. Further, the countdown timer of step 940 and the interval ofstep 945 assist in distributing data/query traffic among all of the enddevices, so that different end devices are able to listen and/ordownload at different intervals. Control then passes to decision step965, which determines if there is an outcome or not based on a responsefrom the central control unit (e.g., 730 in FIG. 7). If there is anoutcome, Yes, indicating that there are changes, control returns to step925. If there is not an outcome, No, indicating that there are no newchange, control passes to step 935.

Returning to step 915, if there are issues identified in theself-diagnostic test, Yes, control passes from step 915 to step 950,which reports the status of the end device to the central server.Control then passes to step 955, which disables the affected feature.Control then passes to step 920.

Returning to step 930, if the outcome is OFF, control passes to step941, which activates a countdown timer. Control then passes to step 946,which determines use. If use is Yes, control passes to step 935.However, if use is No, control returns to step 920.

The power management system of the present disclosure may be practisedusing a computing device, such as a general purpose computer or computerserver. FIG. 12 is a schematic block diagram of a system 1200 thatincludes a general purpose computer 1210. The general purpose computer1210 includes a plurality of components, including: a processor 1212, amemory 1214, a storage medium 1216, input/output (I/O) interfaces 1220,and input/output (I/O) ports 1222. Components of the general purposecomputer 1210 generally communicate using one or more buses 1248.

The memory 1214 may be implemented using Random Access Memory (RAM),Read Only Memory (ROM), or a combination thereof. The storage medium1216 may be implemented as one or more of a hard disk drive, a solidstate “flash” drive, an optical disk drive, or other storage means. Thestorage medium 1216 may be utilised to store one or more computerprograms, including an operating system, software applications, anddata. In one mode of operation, instructions from one or more computerprograms stored in the storage medium 1216 are loaded into the memory1214 via the bus 1248. Instructions loaded into the memory 1214 are thenmade available via the bus 1248 or other means for execution by theprocessor 1212 to implement a mode of operation in accordance with theexecuted instructions.

One or more peripheral devices may be coupled to the general purposecomputer 1210 via the I/O ports 1222. In the example of FIG. 12, thegeneral purpose computer 1210 is coupled to each of a speaker 1224, acamera 1226, a display device 1230, an input device 1232, a printer1234, and an external storage medium 1236. The speaker 1224 may beimplemented using one or more speakers, such as in a stereo or surroundsound system.

The camera 1226 may be a webcam, or other still or video digital camera,and may download and upload information to and from the general purposecomputer 1210 via the I/O ports 1222, dependent upon the particularimplementation. For example, images recorded by the camera 1226 may beuploaded to the storage medium 1216 of the general purpose computer1210. Similarly, images stored on the storage medium 1216 may bedownloaded to a memory or storage medium of the camera 1226. The camera1226 may include a lens system, a sensor unit, and a recording medium.

The display device 1230 may be a computer monitor, such as a cathode raytube screen, plasma screen, or liquid crystal display (LCD) screen. Thedisplay 1230 may receive information from the computer 1210 in aconventional manner, wherein the information is presented on the displaydevice 1230 for viewing by a user. The display device 1230 mayoptionally be implemented using a touch screen to enable a user toprovide input to the general purpose computer 1210. The touch screen maybe, for example, a capacitive touch screen, a resistive touchscreen, asurface acoustic wave touchscreen, or the like.

The input device 1232 may be a keyboard, a mouse, a stylus, drawingtablet, or any combination thereof, for receiving input from a user. Theexternal storage medium 1236 may include an external hard disk drive(HDD), an optical drive, a floppy disk drive, a flash drive, solid statedrive (SSD), or any combination thereof and may be implemented as asingle instance or multiple instances of any one or more of thosedevices. For example, the external storage medium 1236 may beimplemented as an array of hard disk drives.

The I/O interfaces 1220 facilitate the exchange of information betweenthe general purpose computing device 1210 and other computing devices.The I/O interfaces may be implemented using an internal or externalmodem, an Ethernet connection, or the like, to enable coupling to atransmission medium. In the example of FIG. 12, the I/O interfaces 1222are coupled to a communications network 1238 and directly to a computingdevice 1242. The computing device 1242 is shown as a personal computer,but may be equally be practised using a smartphone, laptop, or a tabletdevice. Direct communication between the general purpose computer 1210and the computing device 1242 may be implemented using a wireless orwired transmission link.

The communications network 1238 may be implemented using one or morewired or wireless transmission links and may include, for example, adedicated communications link, a local area network (LAN), a wide areanetwork (WAN), the Internet, a telecommunications network, or anycombination thereof. A telecommunications network may include, but isnot limited to, a telephony network, such as a Public Switch TelephonyNetwork (PSTN), a mobile telephone cellular network, a short messageservice (SMS) network, or any combination thereof. The general purposecomputer 1210 is able to communicate via the communications network 1238to other computing devices connected to the communications network 1238,such as the mobile telephone handset 1244, the touchscreen smartphone1246, the personal computer 1240, and the computing device 1242.

One or more instances of the general purpose computer 1210 may beutilised to implement a server acting as a control data server toimplement a power management system in accordance with the presentdisclosure. In such an embodiment, the memory 1214 and storage 1216 areutilised to store data relating to power information for one or moreinstallations, such as desks in an office workspace. Software forimplementing the power management system is stored in one or both of thememory 1214 and storage 1216 for execution on the processor 1212. Thesoftware includes computer program code for implementing method steps inaccordance with the method of power monitoring described herein.

FIG. 13 is a schematic block diagram of a system 1300 on which one ormore aspects of a power monitoring method and system of the presentdisclosure may be practised. The system 1300 includes a portablecomputing device in the form of a smartphone 1310, which may be used bya registered user of the power monitoring system in FIG. 7. Thesmartphone 1310 includes a plurality of components, including: aprocessor 1312, a memory 1314, a storage medium 1316, a battery 1318, anantenna 1320, a radio frequency (RF) transmitter and receiver 1322, asubscriber identity module (SIM) card 1324, a speaker 1326, an inputdevice 1328, a camera 1330, a display 1332, and a wireless transmitterand receiver 1334. Components of the smartphone 1310 generallycommunicate using one or more bus connections 1348 or other connectionstherebetween. The smartphone 1310 also includes a wired connection 1345for coupling to a power outlet to recharge the battery 1318 or forconnection to a computing device, such as the general purpose computer1210 of FIG. 12. The wired connection 1345 may include one or moreconnectors and may be adapted to enable uploading and downloading ofcontent from and to the memory 1314 and SIM card 1324.

The smartphone 1310 may include many other functional components, suchas an audio digital-to-analogue and analogue-to-digital converter and anamplifier, but those components are omitted for the purpose of clarity.However, such components would be readily known and understood by aperson skilled in the relevant art.

The memory 1314 may include Random Access Memory (RAM), Read Only Memory(ROM), or a combination thereof. The storage medium 1316 may beimplemented as one or more of a solid state “flash” drive, a removablestorage medium, such as a Secure Digital (SD) or microSD card, or otherstorage means. The storage medium 1316 may be utilised to store one ormore computer programs, including an operating system, softwareapplications, and data. In one mode of operation, instructions from oneor more computer programs stored in the storage medium 1316 are loadedinto the memory 1314 via the bus 1348. Instructions loaded into thememory 1314 are then made available via the bus 1348 or other means forexecution by the processor 1312 to implement a mode of operation inaccordance with the executed instructions.

The smartphone 1310 also includes an application programming interface(API) module 1336, which enables programmers to write softwareapplications to execute on the processor 1312. Such applications includea plurality of instructions that may be pre installed in the memory 1314or downloaded to the memory 1314 from an external source, via the RFtransmitter and receiver 1322 operating in association with the antenna1320 or via the wired connection 1345.

The smartphone 1310 further includes a Global Positioning System (GPS)location module 1338. The GPS location module 1338 is used to determinea geographical position of the smartphone 1310, based on GPS satellites,cellular telephone tower triangulation, or a combination thereof. Thedetermined geographical position may then be made available to one ormore programs or applications running on the processor 1312.

The wireless transmitter and receiver 1334 may be utilised tocommunicate wirelessly with external peripheral devices via Bluetooth,infrared, or other wireless protocol. In the example of FIG. 13, thesmartphone 1310 is coupled to each of a printer 1340, an externalstorage medium 1344, and a computing device 1342. The computing device1342 may be implemented, for example, using the general purpose computer1210 of FIG. 12.

The camera 1330 may include one or more still or video digital camerasadapted to capture and record to the memory 1314 or the SIM card 1324still images or video images, or a combination thereof. The camera 1330may include a lens system, a sensor unit, and a recording medium. A userof the smartphone 1310 may upload the recorded images to anothercomputer device or peripheral device using the wireless transmitter andreceiver 1334, the RF transmitter and receiver 1322, or the wiredconnection 1345.

In one example, the display device 1332 is implemented using a liquidcrystal display (LCD) screen. The display 1332 is used to displaycontent to a user of the smartphone 1310. The display 1332 mayoptionally be implemented using a touch screen, such as a capacitivetouch screen or resistive touchscreen, to enable a user to provide inputto the smartphone 1310.

The input device 1328 may be a keyboard, a stylus, or microphone, forexample, for receiving input from a user. In the case in which the inputdevice 1328 is a keyboard, the keyboard may be implemented as anarrangement of physical keys located on the smartphone 1310.Alternatively, the keyboard may be a virtual keyboard displayed on thedisplay device 1332.

The SIM card 1324 is utilised to store an International MobileSubscriber Identity (IMSI) and a related key used to identify andauthenticate the user on a cellular network to which the user hassubscribed. The SIM card 1324 is generally a removable card that can beused interchangeably on different smartphone or cellular telephonedevices. The SIM card 1324 can be used to store contacts associated withthe user, including names and telephone numbers. The SIM card 1324 canalso provide storage for pictures and videos. Alternatively, contactscan be stored on the memory 1314.

The RF transmitter and receiver 1322, in association with the antenna1320, enable the exchange of information between the smartphone 1310 andother computing devices via a communications network 1390. In theexample of FIG. 13, RF transmitter and receiver 1322 enable thesmartphone 1310 to communicate via the communications network 1390 witha cellular telephone handset 1350, a smartphone or tablet device 1352, acomputing device 1354 and the computing device 1342. The computingdevices 1354 and 1342 are shown as personal computers, but each may beequally be practised using a smartphone, laptop, or a tablet device.

The communications network 1390 may be implemented using one or morewired or wireless transmission links and may include, for example, acellular telephony network, a dedicated communications link, a localarea network (LAN), a wide area network (WAN), the Internet, atelecommunications network, or any combination thereof. Atelecommunications network may include, but is not limited to, atelephony network, such as a Public Switch Telephony Network (PSTN), acellular (mobile) telephone cellular network, a short message service(SMS) network, or any combination thereof.

FIG. 18 is a schematic block diagram representation of a powermanagement device embodied in a power board 1800, with a separate powermeter for each power outlet. The power board 1800, also known as a powerstrip, receives an AC mains supply 1805, which is coupled to an inputconnector 1806. The connector 1806 couples to a top power rail 1890 thatfeeds each of a first power outlet 1810, a second power outlet 1820, athird power outlet 1830, and a fourth power outlet 1840, all of whichare connected in parallel.'

The output of the first power outlet 1810 is connected via a first powermeter 1812 to a first relay 1815, which is coupled to a bottom powerrail 1895 that returns to the input connector 1806 in order to completethe circuit. The output of the second power outlet 1820 is connected viaa second power meter 1822 to a second relay 1825. The output of thethird power outlet 1830 is connected via a third power meter 1832 to athird relay 1835. The output of the fourth power outlet 1840 isconnected via a fourth power meter 1834 to a fourth relay 1845. Theoutputs of the second, third, and fourth relays 1825, 1835, and 1845 areall coupled to the bottom power rail 1895.

The power board 1800 further includes a transmitter 1855, which isadapted to couple the power board 1800 to an external communicationsnetwork. The transmitter 1855 may be implemented using wired or wirelesstechnologies, including, but not limited to, Ethernet, Universal SerialBus (USB), Wi-Fi, Bluetooth, ZigBee, SigFox, LoRa, 6LoWPAN, and thelike.

The power board 1800 also includes a microcontroller 1850, which iscoupled to the transmitter 1855. Where the transmitter 1855 isimplemented as a transceiver, an external user can send control signalsvia the external communications network to the transmitter 1855 and thento the microcontroller 1850. The microcontroller 1850 is also coupled toeach of the relays 1815, 1825, 1835, and 1845, via respective controllines 1865, 1870, 1875, 1880 which enable the microcontroller 1850 tocontrol the application of power to each of the respective power outlets1810, 1820, 1830, 1840.

In an alternative embodiment (not shown), a single relay controls theapplication of power to each of the set of power outlets 1810, 1820,1830, 1840. In such an arrangement, all of the power outlets 1810, 1820,1830, 1840 are controlled together, such that the power outlets 1810,1820, 1830, 1840 are all turned on or all turned off. In the arrangementshown in FIG. 18, the microcontroller 1850 is able to control power tothe power outlets 1810, 1820, 1830, 1840 independently.

The first, second, third, and fourth power meters 1812, 1822, 1832, 1842record the individual power consumption for the respective power outlets1810, 1820, 1830, 1840 and transmit recorded power information to themicrocontroller 1850. The microcontroller 1850 sends some or all of therecorded power information to the transmitter 1855 for transmission to aremote server.

FIG. 19 is a schematic diagram illustrating a power management systemwith a power management device with an identification service. In theembodiment shown, a power management device 1902 receives power from apower source 1904 (e.g., a wall socket, battery, fuel cell, etc.) andcommunicates with a network service 1906 through a network 1912 (such asthe Internet or an intranet). The power management device 1902 receivespower through a power interface 1914 and communicates with the networkservice 1906 through a network interface 1918. A microcontroller 1916can be coupled to the power interface 1914, the network interface 1918,a sensor array 1920 and configurable state power connectors 1922. Theconfigurable state power connectors 1922 are coupled to receptacles 1924that electrically power and couple to devices 1926, 1928 and 1930.

The network service 1906 is coupled to the network 1912 and includesconnections to a configuration database 1908 and an identificationdatabase 1910. The network service 1906 can include managementfunctionality that allows for receipt of reports from a set of powermanagement devices and for providing configuration and/or commands tothe set of power management devices. The network service 1906 can alsoprovide reporting, data aggregation and/or management functionality forone or more power management devices 1902.

In one embodiment, the configurable state power connectors 1924 are inan “on” state that enables power from the power interface 1914 to beprovided through the receptacles 1924. The sensor array 1920 detects a“power on” event at one of the receptacles 1924 from the device 1926drawing power. A power demand over time waveform is sampled by thesensor array 1920 during the power on event and provided to themicrocontroller 1916. The microcontroller 1916 constructs a message thatincludes the power demand over time waveform to deliver to the networkservice 1906 using the network interface 1918 coupled to the network1912.

The network service 1906 can match the power demand over time waveformto a power profile stored in the identification database 1910. Based onthe identification (or lack of identification), a configuration for thepower management device 1902 can be created based on data from theconfiguration database 1908. For example, the detected device can be aprinter, and an outlet of the power management device 1902 can beassigned a printer tag. A configuration for the power management device1902 can be altered to include a “power off” state during specifiednighttime hours (e.g., 10 pm-5 am).

The network service 1906 can provide the configuration to the powermanagement device 1902 through the network interface 1918. Themicrocontroller 1916 can store the configuration and operate theconfigurable state power connectors 1922 based on the configuration.

In some embodiments, the configuration can include parameters about whenthe configurable state power connectors 1922 can be on or off and whenthe sensor array 1920 samples power draw from the devices 1926, 1928 and1930 plugged into the receptacles 1924.

FIG. 20 is a schematic diagram illustrating a power management systemwith a power management device with local identification. In theembodiment shown, a power management device 2002 receives power from apower source 2004 (e.g., a wall socket, battery, fuel cell, etc.) andcommunicates with a network service 2006 through a network 2012 (such asthe Internet or an intranet). The power management device 2002 receivespower through a power interface 2014 and communicates with the networkservice 2006 through a network interface 2018. A microcontroller 2016can be coupled to the power interface 2014, the network interface 2018,a sensor array 2020, configurable state power connectors 2022, anidentification database 2040 and a configuration database 2042. Theconfigurable state power connectors 2022 are coupled to receptacles 2024that electrically power and couple to devices 2026, 2028 and 2030.

The network service 2006 is coupled to the network 2012 and can providereporting, data aggregation and/or management functionality for one ormore power management devices 2002. The network service 2006 can includemanagement functionality that allows for receipt of reports from a setof power management devices and providing configuration and/or commandsto the set of power management devices.

In one embodiment, the configurable state power connectors 2024 are inan “on” state that enables power from the power interface 2014 to beprovided through the receptacles 2024. The sensor array 2020 detects a“power on” event at one of the receptacles 2024 from the device 2026drawing power. A power demand over time waveform is sampled by thesensor array 2020 during the power on event and provided to themicrocontroller 2016. The microcontroller 2016 matches the power demandover time waveform to a power profile stored in the identificationdatabase 2040. Based on the identification (or lack of identification),a configuration for the power management device 2002 can be createdbased on data from the configuration database 2042. For example, thedetected device can be a printer, and an outlet of the power managementdevice 2002 can be assigned a printer tag that is reported to thenetwork service 2006. A configuration for the power management device2002 can be altered to include a “power off” state during specifiednighttime hours (e.g., 10 pm-5 am).

The network service 2006 can provide updates to the configurationdatabase 2042 and/or the identification database 2040 of the powermanagement device 2002 through the network interface 2018. Themicrocontroller 2016 can verify, store and/or apply the updates tocurrent configurations (e.g., rebuild configurations).

In some embodiments, the configuration can include parameters about whenthe configurable state power connectors 2022 can be on or off and whenthe sensor array 2020 samples power draw from the devices 2026, 2028 and2030 plugged into the receptacles 2024.

FIG. 21 is a diagram 2100 illustrating status determination using powerthresholds consistent with embodiments disclosed herein. A powermanagement device can also determine status of an identified deviceplugged into the power management device based on power usage of theidentified device. In the embodiment shown, an operating power profileof a device can include a plurality of thresholds that identify statusof the device. Between a high operating threshold 2112 and a lowoperating threshold 2116, a power signature 2114 of the device indicatesan operating status 2104 of the device (e.g., a printer printing sheetsof paper, a computer with a user operating it, etc.). Between a highidle threshold 2118 and a low idle threshold 2120, a power signature ofthe device indicates an idle status 2108 of the device (e.g., a printeror computer in standby mode). Below the low idle threshold 2120, thedevice can be considered to be in an off state 2110, and off-state (alsocalled vampiric) power use can be identified. Above the high operatingthreshold 2112, or between the low operating threshold 2116 and the highidle threshold 2118, the device can be considered to be in amalfunctioning state 2102 or 2106. For example, the malfunctioning state2102 can be a paper jam for a printer that causes sudden power draw ofmotors above the high operating threshold 2112, or a computer in themalfunctioning state 2106 may be in a crashed state in which power drawis not as high as in the operating state 2104 or as low as in the idlestate 2108.

Other status determination methods can also be used. For example, adelay can be applied to a threshold, such that sudden operating spikesor transitions between states do not trigger an alarm. In someembodiments, waveform matching can be used. For example, statedetermination can be triggered on a rising wave or falling wave. In someembodiments, the resulting waveform after the rising or falling wave canthen be matched against a stored waveform to determine state. Forexample, a printer might have a warm-up waveform, followed by a printingwaveform, followed by a printing-wrap-up waveform. The statusdetermination can determine which first status the device is in, whichnext status follows it, and a workflow of statuses expected. Deviationfrom an expected status or a status timing beyond a length threshold cantrigger an alarm.

FIG. 22 is a diagram illustrating successful power signatureidentification using a power profile consistent with embodimentsdisclosed herein. The power management device or network service canmatch an actual power signature 2202 to an expected power signature 2204in an identification database. When the signatures match, a device type2200 (such as a model of a device, such as a Dell 1708FP monitor) can beidentified as a device plugged into the power management device. In oneembodiment, the power matching is performed by matching slopes atdefined points. In another embodiment, the power matching is performedby matching portions of an expected power signature plus or minus athreshold value (or between threshold values). Other matching algorithmsare also possible.

FIG. 23 is a diagram 2300 illustrating unsuccessful power signatureidentification using power profiles consistent with embodimentsdisclosed herein. The power management device or network service canattempt to match an actual power signature to an expected powersignature in an identification database. In the embodiment shown, anunknown actual power signature 2302 does not match expected powersignatures of a desktop power signature 2308, a printer power signature2306 or a laptop power signature 2304. In an embodiment using matchingslopes at defined points, the actual power signature 2302 does not matchany of the expected power signatures 2304, 2306 and 2308. In anembodiment using an expected power signature plus or minus a thresholdvalue, the actual power signature 2302 does not match any of theexpected power signatures 2304, 2306 and 2308. In some embodiments, athreshold value can vary, such as a threshold varying based on time orslope.

FIG. 24 is a diagram illustrating a screenshot of a dashboard 2400 usingtag aggregation of power management devices consistent with embodimentsdisclosed herein. In some embodiments, each configurable state powerconnector of a power management device can be associated with one ormore metadata. This metadata can include a tag, which identifies anassociation with a group. Tags can identify models of equipment (e.g.,Dell 1708FP monitor), types of equipment (e.g., monitor, printer, etc.),caretakers or owners of equipment (e.g., Jane Doe), departments (e.g.,marketing, sales, engineering, call center, copy center, admin, IT,etc.), or other groups or associations. Reports of data from the powermanagement device to a network service can identify power usage by tag.

Power usage of these groupings can be aggregated and plotted over time.In the embodiment shown in FIG. 24, department power usage is shown byaggregating power usage based on tags representing departments. Thegraphs can represent average power usage, total power usage or othermeasurements or statistics as configured or requested. Marketing/Salesdepartment usage is shown in a graph 2402. Engineering department usageis shown in a graph 2404. Call center department usage is shown in agraph 2406. Copy center department usage is shown in a graph 2408. Lunchroom usage is shown in a graph 2410. Testing department usage is shownin a graph 2412. Administrative department usage is shown in a graph2414. IT department usage is shown in a graph 2416. The dashboard 2400shows the graphs 2402-2416 on a computer screen, as presented by anetwork service that aggregated the data. This data can be used forcapital planning, including power needs (peak and average), as well aspotential areas for power reduction.

FIG. 25 is a diagram illustrating a screenshot 2500 of an enhanced assetmanagement system. In one embodiment, an asset management system can tageach configurable state power connector of a power management devicewith asset information, such as asset name, asset tag and device type.During inventory, a power management system can identify device typescoupled to each configurable state power connector and report back tothe enhanced asset management system. If the device detected matches adevice type tag, then the device is likely the asset expected and can beconfirmed. This allows inventory management to focus on mismatchesrather than verifying each and every asset tag.

In another embodiment, an asset management system can list devices thatare associated with people, desks or places. As the person or desk isassigned equipment, a power management device can also be associatedwith the people, desk or place. During inventory, a power managementsystem can identify device types coupled to each configurable statepower connector and report back to the enhanced asset management system.If the device detected matches a device type tag associated with theperson, desk or place, then the device is likely the asset expected andcan be confirmed. This allows inventory management to focus onmismatches rather than verifying each and every asset tag.

FIG. 26 is a system diagram illustrating a system 2600 configured toprovide services to a power management device consistent withembodiments disclosed herein. A power management device can communicatewith a service 2616 over the Internet 2614 as described above. Theservice 2616 can include load balancers 2602 capable of decryption,application servers 2604, storage 2606, a control server 2610 and/or alogging server 2608. The load balancers 2602 can receive requests frompower management device systems and format the requests to be receivedby the application servers 2604. The application servers 2604 canreceive data from the power management device systems, cause data to bestored by the data servers 2606 and provide administrative reports. Theapplication servers 2604 can provide results (such as aggregated data,average power reports, dashboards, etc.) to the load balancers 2602,which transmit the results to administrative systems. The databaseservers 2606 can store data regarding the power management devices,tags, configurable state power connectors, power management deviceconfigurations, power profiles and/or account information. The controlserver 2610 can monitor systems of the service 2616 and/or cause serversto be added to pools of servers (such as the load balancers 2602, theapplication servers 2604 and/or the database servers 2606). The controlserver 2610 can also provide data integrity/redundancy services such ascausing snapshotting, caching and/or other features. The logging server2608 can track usage and operations performed by the service 2616 and onbehalf of the service 2616.

In one example, a user can set up an account with the service 2616 usingan application on a mobile device. The user registers an account withthe service 2616. The service 2616 can store user credentials in thestorage 2606.

FIG. 27 is a flow chart 2700 illustrating a method for power managementconsistent with embodiments disclosed herein. The method can beaccomplished by a power management device and network service asdescribed in FIGS. 1 and/or 2. In block 2702, a power management devicedetects a “power on” event of a device electrically coupled to anelectronically configurable power connection. In block 2704, the powermanagement device samples power usage proximate to the power on eventfor a period and for the device electrically coupled to theelectronically configurable power connection. In block 2706, the powermanagement device determines a power on signature from a set of power onsignatures that matches the sampled power usage of the device proximateto the power on event. In block 2708, the power management devicedetermines a device identifier associated with the power on signaturethat matches the sampled power usage.

FIG. 28 is a schematic diagram of a computing system 2800 consistentwith embodiments disclosed herein. The computing system 2800 can beviewed as an information passing bus that connects various components.In the embodiment shown, the computing system 2800 includes a processorhaving logic 2802 for processing instructions. Instructions can bestored in and/or retrieved from a memory 2806 and a storage device 2808that includes a computer-readable storage medium. Instructions and/ordata can arrive from a network interface 2810 that can include wired2814 or wireless 2812 capabilities. Instructions and/or data can alsocome from an I/O interface 2816 that can include such things asexpansion cards, secondary buses (e.g., USB, etc.), devices, etc. A usercan interact with the computing system 2800 though user interfacedevices 2818 and a rendering system 2804 that allows the computer toreceive and provide feedback to the user.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 is a system for providing a status of a remote device. Thesystem includes a set of designable power connectors designed to providepower to removably electrically attached devices, the designable powerconnectors electronically switchable to on and off states, and a set ofsensors attached to the set of designable power connectors, the set ofsensors designed to sample an energy consumption characteristic of thedevices electrically attached to the set of designable power connectorsand designed to transmit sampled energy consumption characteristic data.The system includes a processing unit designed to receive first sampledenergy consumption characteristic data from the set of sensors anddetermine a first device energy consumption profile of a first deviceattached to a first power connector sampled by a first sensor from theset of sensors. The system includes a processing unit designed to matchthe first sampled energy consumption characteristic data to a firststatus described in the first device energy consumption profile anddetermine whether to perform a first follow-up action based at least inpart on the first status.

Example 2 is the system of Example 1, where the energy consumptioncharacteristic includes a power profile.

Example 3 is the system of Example 1, where the energy consumptioncharacteristic includes instantaneous voltage, average voltage,instantaneous amperage, instantaneous wattage or average wattage.

Example 4 is the system of Example 1, where the energy consumptioncharacteristics includes power profile, current profile, electronicssignature, electronic waveform or device temperature.

Example 5 is the system of Example 1, further comprising a networkinterface designed to communicate with a network service, the networkservice designed to receive energy consumption reports from the system.

Example 6 is the system of Example 5, where the processing unit isfurther designed to transmit the status to the network service.

Example 7 is the system of Example 5, where the status includes: idling,operating, malfunctioning or off.

Example 8 is the system of Example 1, where to match the first sampledenergy consumption characteristic usage data to the first statusdescribed in the first device energy consumption profile furtherincludes to determine that the first sampled energy consumption usagedata is between an upper status threshold and a lower status threshold.

Example 9 is the system of Example 1, where to determine whether toperform the first follow-up action further includes looking up a statusin a reaction database, receiving an associated action from the reactiondatabase, and executing the associated action based at least in part onthe status and the first power connector.

Example 10 is the system of Example 1, where the action is toelectronically switch off power to the first power connector, transmitan alert message, or perform a time-delayed action.

Example 11 is a network service for managing power consumption. Thenetwork includes an application program interface (API) designed toreceive power data from a variety of remote power monitoring devices andstorage for storing received power data. The network includes aprocessor unit attached to the API and the storage, the processor unitdesigned to receive a set of power data from the API, the set of powerdata describing power draw of the variety of remote power monitoringdevices over a period of time, aggregate the set of power data to formsubsets of power data based on attributes associated with the remotepower monitoring devices, and render at least some of the subsets ofpower data for display on a display device of a computing resourceexecuting a power management application.

Example 12 is the network service of Example 11, where the powermanagement application is a web-based application.

Example 13 is the network service of Example 11, where the attributesare tags applied to the remote power monitoring devices or tags appliedto power couplings of the remote power monitoring devices.

Example 14 is a computer program product including a computer-readablestorage medium that stores instructions for execution by a processor toperform operations of a power monitoring equipment, the operations, whenexecuted by the processor, to perform a method. The method includesdetecting a power on event of a device electrically attached to anelectronically designable power connection and sampling energyconsumption proximate to the power on event for a period and for thedevice electrically attached to the electronically designable powerconnection. The method includes determining a power on signature from aset of power on signatures that matches the sampled energy consumptionof the device proximate to the power on event, and determining a deviceidentifier associated with the power on signature that matches thesampled energy consumption.

Example 15 is the computer program product of Example 14, where samplingenergy consumption further includes sampling instantaneous voltage,average voltage, instantaneous amperage, instantaneous wattage oraverage wattage.

Example 16 is the computer program product of Example 14, where thepower on signature includes a power profile, current profile,electronics signature, electronic waveform or device temperature.

Example 17 is the computer program product of Example 14, where themethod further includes transmitting an indicator of the deviceidentifier to a network service.

Example 18 is the computer program product of Example 15, where themethod further includes receiving an action to implement from thenetwork service based on the device identifier.

Example 19 is the computer program product of Example 16, where theaction is performing periodic reporting, transmitting an alert, turningoff the electronically designable power connection or performing atime-delayed action.

Example 20 is a network service for device auditing. The networkincludes an application program interface (API) designed to receivepower data from a variety of remote power monitoring devices, andstorage for storing received power data. The network includes aprocessor unit attached to the API and the storage, the processor unitdesigned to receive a set of power data from the API, the set of powerdata identifying device models drawing power from the variety of remotepower monitoring devices over a period of time based at least in part ona match between a sampled power usage and a device model power usageprofile, and determine a set of detected device models attached to anindividual power monitoring device. The network includes a processorunit attached to the API and the storage, the processor unit designed todetermine which of the set of detected device models matches a set ofexpected models for the individual power monitoring device based atleast in part on the set of power data, provide a set of indications ofconfirmation that includes an indication of confirmation for eachdetected device model of the set of detected device models that matchesan element of the set of expected models for the individual powermonitoring device, and store audit data comprising the indications ofconfirmation, the set of detected device models and the set of expectedmodels to computer readable media.

Example 21 is the apparatus of Example 18, where the API is furtherdesigned to also receive power usage, electrical data or metadata fromthe variety of remote power monitoring devices.

Example 22 is the apparatus of Example 18, where a subset of powercouplings of the variety of remote power monitoring devices areassociated with a set of inventory management tags, an inventorymanagement tag stored locally on a remote power monitoring device.

Example 23 is the apparatus of Example 18, where the audit data isstored as a spreadsheet.

Example 24 is the apparatus of Example 20, where the spreadsheetincludes columns for the indications of confirmation, the set ofdetected device models and set of expected models to computer readablemedia for the variety of remote power monitoring devices.

INDUSTRIAL APPLICABILITY

The arrangements described are applicable to the power industry.

The foregoing describes only some embodiments of the present invention,and modifications and/or changes can be made thereto without departingfrom the scope and spirit of the invention, the embodiments beingillustrative and not restrictive.

In the context of this specification, the word “comprising” and itsassociated grammatical constructions mean “including principally but notnecessarily solely” or “having” or “including,” and not “consisting onlyof.” Variations of the word “comprising,” such as “comprise” and“comprises,” have correspondingly varied meanings.

As used throughout this specification, unless otherwise specified, theuse of ordinal adjectives “first,” “second,” “third,” “fourth,” etc., todescribe common or related objects, indicates that reference is beingmade to different instances of those common or related objects, and isnot intended to imply that the objects so described must be provided orpositioned in a given order or sequence, either temporally, spatially,in ranking, or in any other manner.

Although the invention has been described with reference to specificexamples, it will be appreciated by those skilled in the art that theinvention may be embodied in many other forms.

Embodiments and implementations of the systems and methods describedherein may include various operations, which may be embodied inmachine-executable instructions to be executed by a computer system. Acomputer system may include one or more general-purpose orspecial-purpose computers (or other electronic devices). The computersystem may include hardware components that include specific logic forperforming the operations or may include a combination of hardware,software, and/or firmware.

Computer systems and the computers in a computer system may be connectedvia a network. Suitable networks for configuration and/or use asdescribed herein include one or more local area networks, wide areanetworks, metropolitan area networks, and/or Internet or IP networks,such as the World Wide Web, a private Internet, a secure Internet, avalue-added network, a virtual private network, an extranet, anintranet, or even stand-alone machines which communicate with othermachines by physical transport of media. In particular, a suitablenetwork may be formed from parts or entireties of two or more othernetworks, including networks using disparate hardware and networkcommunication technologies.

One suitable network includes a server and one or more clients; othersuitable networks may contain other combinations of servers, clients,and/or peer-to-peer nodes, and a given computer system may function bothas a client and as a server. Each network includes at least twocomputers or computer systems, such as the server and/or clients. Acomputer system may include a workstation, laptop computer,disconnectable mobile computer, server, mainframe, cluster, so-called“network computer” or “thin client,” tablet, smartphone, personaldigital assistant or other hand-held computing device, “smart” consumerelectronics device or appliance, medical device, or a combinationthereof.

Suitable networks may include communications or networking software,such as the software available from Novell®, Microsoft®, and othervendors, and may operate using TCP/IP, SPX, IPX, and other protocolsover twisted pair, coaxial, or optical fiber cables, telephone lines,radio waves, satellites, microwave relays, modulated AC power lines,physical media transfer, and/or other data transmission “wires” known tothose of skill in the art. The network may encompass smaller networksand/or be connectable to other networks through a gateway or similarmechanism.

Various techniques, or certain aspects or portions thereof, may take theform of program code (i.e., instructions) embodied in tangible media,such as floppy diskettes, CD-ROMs, hard drives, magnetic or opticalcards, solid-state memory devices, a nontransitory computer-readablestorage medium, or any other machine-readable storage medium wherein,when the program code is loaded into and executed by a machine, such asa computer, the machine becomes an apparatus for practicing the varioustechniques. In the case of program code execution on programmablecomputers, the computing device may include a processor, a storagemedium readable by the processor (including volatile and nonvolatilememory and/or storage elements), at least one input device, and at leastone output device. The volatile and nonvolatile memory and/or storageelements may be a RAM, an EPROM, a flash drive, an optical drive, amagnetic hard drive, or other medium for storing electronic data. One ormore programs that may implement or utilize the various techniquesdescribed herein may use an application programming interface (API),reusable controls, and the like. Such programs may be implemented in ahigh-level procedural or an object-oriented programming language tocommunicate with a computer system. However, the program(s) may beimplemented in assembly or machine language, if desired. In any case,the language may be a compiled or interpreted language, and combinedwith hardware implementations.

Each computer system includes one or more processors and/or memory;computer systems may also include various input devices and/or outputdevices. The processor may include a general purpose device, such as anIntel®, AMD®, or other “off-the-shelf” microprocessor. The processor mayinclude a special purpose processing device, such as ASIC, SoC, SiP,FPGA, PAL, PLA, FPLA, PLD, or other customized or programmable device.The memory may include static RAM, dynamic RAM, flash memory, one ormore flip-flops, ROM, CD-ROM, DVD, disk, tape, or magnetic, optical, orother computer storage medium. The input device(s) may include akeyboard, mouse, touch screen, light pen, tablet, microphone, sensor, orother hardware with accompanying firmware and/or software. The outputdevice(s) may include a monitor or other display, printer, speech ortext synthesizer, switch, signal line, or other hardware withaccompanying firmware and/or software.

It should be understood that many of the functional units described inthis specification may be implemented as one or more components, whichis a term used to more particularly emphasize their implementationindependence. For example, a component may be implemented as a hardwarecircuit comprising custom very large scale integration (VLSI) circuitsor gate arrays, or off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. A component may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices, orthe like.

Components may also be implemented in software for execution by varioustypes of processors. An identified component of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object, aprocedure, or a function. Nevertheless, the executables of an identifiedcomponent need not be physically located together, but may comprisedisparate instructions stored in different locations that, when joinedlogically together, comprise the component and achieve the statedpurpose for the component.

Indeed, a component of executable code may be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within components, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork. The components may be passive or active, including agentsoperable to perform desired functions.

Several aspects of the embodiments described will be illustrated assoftware modules or components. As used herein, a software module orcomponent may include any type of computer instruction orcomputer-executable code located within a memory device. A softwaremodule may, for instance, include one or more physical or logical blocksof computer instructions, which may be organized as a routine, program,object, component, data structure, etc., that perform one or more tasksor implement particular data types. It is appreciated that a softwaremodule may be implemented in hardware and/or firmware instead of or inaddition to software. One or more of the functional modules describedherein may be separated into sub-modules and/or combined into a singleor smaller number of modules.

In certain embodiments, a particular software module may includedisparate instructions stored in different locations of a memory device,different memory devices, or different computers, which togetherimplement the described functionality of the module. Indeed, a modulemay include a single instruction or many instructions, and may bedistributed over several different code segments, among differentprograms, and across several memory devices. Some embodiments may bepracticed in a distributed computing environment where tasks areperformed by a remote processing device linked through a communicationsnetwork. In a distributed computing environment, software modules may belocated in local and/or remote memory storage devices. In addition, databeing tied or rendered together in a database record may be resident inthe same memory device, or across several memory devices, and may belinked together in fields of a record in a database across a network.

Reference throughout this specification to “an example” means that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one embodiment of the presentinvention. Thus, appearances of the phrase “in an example” in variousplaces throughout this specification are not necessarily all referringto the same embodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based onits presentation in a common group without indications to the contrary.In addition, various embodiments and examples of the present inventionmay be referred to herein along with alternatives for the variouscomponents thereof. It is understood that such embodiments, examples,and alternatives are not to be construed as de facto equivalents of oneanother, but are to be considered as separate and autonomousrepresentations of the present invention.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of materials, frequencies, sizes, lengths, widths, shapes,etc., to provide a thorough understanding of embodiments of theinvention. One skilled in the relevant art will recognize, however, thatthe invention may be practiced without one or more of the specificdetails, or with other methods, components, materials, etc. In otherinstances, well-known structures, materials, or operations are not shownor described in detail to avoid obscuring aspects of the invention.

It should be recognized that the systems described herein includedescriptions of specific embodiments. These embodiments can be combinedinto single systems, partially combined into other systems, split intomultiple systems or divided or combined in other ways. In addition, itis contemplated that parameters/attributes/aspects/etc. of oneembodiment can be used in another embodiment. Theparameters/attributes/aspects/etc. are merely described in one or moreembodiments for clarity, and it is recognized that theparameters/attributes/aspects/etc. can be combined with or substitutedfor parameters/attributes/etc. of another embodiment unless specificallydisclaimed herein.

Although the foregoing has been described in some detail for purposes ofclarity, it will be apparent that certain changes and modifications maybe made without departing from the principles thereof. It should benoted that there are many alternative ways of implementing both theprocesses and apparatuses described herein. Accordingly, the presentembodiments are to be considered illustrative and not restrictive, andthe invention is not to be limited to the details given herein, but maybe modified within the scope and equivalents of the appended claims.

Those having skill in the art will appreciate that many changes may bemade to the details of the above-described embodiments without departingfrom the underlying principles of the invention. The scope of thepresent invention should, therefore, be determined only by the followingclaims.

1. A system for asset management comprising: a plurality of powermanagement devices, each power management device configured to:removably electrically couple to a power distribution socket; providepower to one or more removably electrically coupled devices; record aset of power profiles, each power profile corresponding to one of theone or more removably electrically coupled devices; and transmit the setof power profiles to an identification service; the identificationservice comprising storage for model power profiles of a plurality ofdevices and one or more processors configured to: process the set ofpower profiles from the plurality of power management devices; determinewhether a match exists between a power profile from the set of powerprofiles and a model power profile from a set of model power profiles;and when the match exists, add an association, to a set of associations,of a power management device from the plurality of power managementdevices to a device represented by the model power profile; an assetmanagement service configured to: process an asset list comprising a setof asserted associations of devices coupled to power management devices;and create an asset report of matches between the set of assertedassociations with the set of associations.
 2. The system of claim 1,wherein the power management devices comprise a power strip with powersockets configured to receive power plugs from the one or more removablyelectrically coupled devices.
 3. The system of claim 1, wherein thepower management devices comprise a network interface configured tocommunicate with the identification service.
 4. The system of claim 1,wherein the set of power profiles are initial power profiles recordedbased on an initial power draw.
 5. The system of claim 1, wherein theset of power profiles are a steady state power profile.
 6. The system ofclaim 1, wherein the identification service is further configured tocreate a missing asset report comprising asserted associations from theset of asserted associations missing from the set of associations. 7.The system of claim 1, wherein the identification service is furtherconfigured to create an extra asset report comprising associations fromthe set of associations missing from the set of asserted associations.8. A network service for device auditing, comprising: an applicationprogram interface (API) configured to receive energy consumption datafrom a plurality of remote energy consumption monitoring devices;storage for storing received energy consumption data; and a processorunit coupled to the API and the storage, the processor unit configuredto: receive a set of energy consumption data from the API, the set ofenergy consumption data identifying device models drawing energy fromthe plurality of remote energy consumption monitoring devices over aperiod of time based at least in part on a match between a sampledenergy consumption usage and a device model energy consumption usageprofile; determine a set of detected device models coupled to anindividual energy consumption monitoring device; determine which of theset of detected device models matches a set of expected models for theindividual energy consumption monitoring device based at least in parton the set of energy consumption data; provide a set of indications ofconfirmation that includes an indication of confirmation for eachdetected device model of the set of detected device models that matchesan element of the set of expected models for the individual energyconsumption monitoring device; and store audit data comprising the setof indications of confirmation, the set of detected device models andthe set of expected models to computer readable media.
 9. The networkservice of claim 8, wherein the API is further configured to alsoreceive energy usage, electrical data or metadata from the plurality ofremote energy consumption monitoring devices.
 10. The network service ofclaim 8, wherein a subset of energy consumption couplings of theplurality of remote energy consumption monitoring devices are associatedwith a set of inventory management tags, an inventory management tagstored locally on a remote energy consumption monitoring device.
 11. Thenetwork service of claim 8, wherein the audit data is stored as aspreadsheet.
 12. The network service of claim 11, wherein thespreadsheet comprises columns for the indications of confirmation, theset of detected device models and the set of expected models to computereadable media for the plurality of remote energy consumption monitoringdevices.
 13. The network service of claim 8, wherein energy consumptionis power draw.
 14. The network service of claim 8, wherein energyconsumption is current draw.
 15. A computer program product comprising acomputer-readable storage medium that stores instructions for executionby a processor to perform operations of an asset management system, theoperations, when executed by the processor, to perform a method, themethod comprising: processing a set of energy consumption profilescreated by a set of remote energy consumption monitoring devices, theset of energy consumption profiles representing energy consumption of anelectrical device coupled to a remote energy consumption monitoringdevice; attempting to match each energy consumption profile of the setof energy consumption profiles to a device model profile from a set ofdevice model profiles, the device model profile describing an energyconsumption of an identified device; when the match occurs between anenergy consumption profile and a device model profile, recording anidentified device as attached to a remote energy consumption monitoringdevice that provided the energy consumption profile; and creating anasset report describing each recording of an identified deviceassociated with a remote energy consumption monitoring device.
 16. Thecomputer program product of claim 15, wherein the set of remote energyconsumption monitoring devices are configured to include tags ofexpected identified devices electrically coupled to the remote energyconsumption monitoring device.
 17. The computer program product of claim15, wherein the set of remote energy consumption monitoring devices areconfigured to include a location or user tag that is correlated to a setof devices that are located at the location or assigned to a user. 18.The computer program product of claim 15, wherein the asset reportfurther shows expected identified devices that were not associated withone or more remote energy consumption monitoring devices.
 19. Thecomputer program product of claim 15, wherein the asset report is aspreadsheet.
 20. The computer program product of claim 15, wherein theset of energy consumption profiles are initial power profiles recordedbased on an initial power draw.
 21. A power management device for deviceauditing, comprising: a power coupling configured to removablyelectrically couple to a power source; a power receptacle configured toremovably electrically couple a device model to the power source; asensor coupled to the power receptacle and configured to record energyconsumption of the device model; storage to store the recorded energyconsumption of the device model; and a network interface configured tocommunicate with a network service for device auditing, the networkinterface configured to transmit the recorded energy consumption of thedevice model to the network service for identification of the devicemodel by comparing the recorded energy consumption with one or moreenergy consumption profiles and for using the identification todetermine the presence of the device model as connected to the powermanagement device.
 22. The power management device of claim 21, whereinthe storage is further configured to store an indicator of an expecteddevice model coupled to the power receptacle.
 23. The power managementdevice of claim 21, wherein the sensor is configured to record aninitial energy consumption of the device model.
 24. The power managementdevice of claim 21, wherein the device model is associated with aninventory management tag, and wherein the inventory management tag isstored locally on the power management device.
 25. The power managementdevice of claim 24, further comprising a processor configured to processa request for the inventory management tag from the network service andgenerate a response including the inventory management tag.
 26. Thepower management device of claim 21, wherein the energy consumption ispower draw.
 27. The power management device of claim 21, wherein theenergy consumption is current draw.
 28. The power management device ofclaim 21, further comprising a set of power receptacles configured toremovably electrically couple a set of device models to the powersource.